Add nosto skill — Nosto frontend JS APIs#245
Open
joseamijares wants to merge 1 commit intovercel-labs:mainfrom
Open
Add nosto skill — Nosto frontend JS APIs#245joseamijares wants to merge 1 commit intovercel-labs:mainfrom
joseamijares wants to merge 1 commit intovercel-labs:mainfrom
Conversation
Reference for integrating Nosto's frontend SDK on a storefront. Covers the legacy nostojs global, the @nosto/nosto-js npm package, and @nosto/nosto-react. SKILL.md is lean: triggers, the Page Tagging vs Session API choice, and the most common patterns inline. Detailed material is split into five reference files for progressive disclosure: - references/initialization.md — loaders, init() options, consent gating - references/session-events.md — defaultSession chain, viewX, addOrder - references/recommendations.md — placements, dynamic filtering, callbacks - references/customer-search-experiments.md — customer ID, GraphQL search - references/patterns-gotchas.md — SPA, multi-store, common bugs Sources: docs.nosto.com/techdocs and nosto.github.io/nosto-js.
|
@joseamijares is attempting to deploy a commit to the Vercel Team on Vercel. A member of the Team first needs to authorize it. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds a new
nostoskill covering Nosto's frontend JavaScript SDK and the@nosto/nosto-jspackage — initialization, session events, recommendation placements, customer/order tracking, and React/Next.js integration via@nosto/nosto-react.Nosto is a widely-used e-commerce personalization platform; agents working on Shopify, BigCommerce, Magento, or headless storefronts often need to wire it up correctly, and the integration has a few non-obvious traps (Page Tagging vs Session API, attribution requiring two calls, PII rules around
customer_reference) that this skill captures explicitly.What's in the skill
SKILL.md(lean — triggers + the most common patterns inline) plus five reference files for progressive disclosure:references/initialization.md— loaders,init()options, GDPR/consent gating, debug modereferences/session-events.md— fulldefaultSessionchain, everyview*,addOrder,setCustomer, cart updatesreferences/recommendations.md—setPlacements,loadRecommendations,createRecommendationRequest, dynamic filtering,prerender/postrendercallbacksreferences/customer-search-experiments.md— customer identification rules, Nosto Search GraphQL, A/B testing surfacesreferences/patterns-gotchas.md— SPA / React integration, multi-store, and the top 10 things developers get wrongStructure mirrors
react-best-practicesandcomposition-patterns(frontmatter withname/description/license/metadata, plus ametadata.jsonwith cited sources).Sources
All content is synthesized from Nosto's official documentation:
Test plan
SKILL.mdfrontmatter hasname+descriptionand is loadablenostojs,nosto-js, "Nosto recommendations", "Nosto session API")references/are linked fromSKILL.md(one level deep, per the repo's context-efficiency guidelines)customer_referenceexamples use UUIDs / hashed IDs)react-best-practicesandcomposition-patterns